Support for Dynamic Client Credentials #77
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
August 2, 2015 13:27
…ynamic credential switching in a multitenant environment
|
actually, there is a way to do that, in the setup phase, see this: https://github.com/intridea/omniauth/wiki/Setup-Phase |
Member
|
Closing based on follow-up comment. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using omniauth in a multitenant environment, it's useful to have a separate set of credentials for each tenant that need to be selected at runtime based on the target domain/path of a request. This change allows the client_id and client_secret settings to be passed as anonymous functions instead of static values in order to facilitate this.